@LukeSeifert Thanks for the quick review! I added documentation to the markdown files and I renamed the variables to _penalty and _postprocessor. I think the MOOSE team used to be more lax about variables names. To be fair the names usually quite obvious (e.g. _t usually means time). As the framework grew over the years, naming conflicts have cropped up. However, it can be difficult to "rectify" some of the names without impacting a large number of users and MOOSE-based apps downstream.

Feel free to merge if you approve!

I think the MOOSE team used to be more lax about variables names.

@LukeSeifert @smpark7 I have no doubt that we might have been a bit more lax in the past. 😄 The decision on _t was a decent bit before my time though. I would like to think that short-named spatial and temporal variables that get inherited (like _t) come from how one naturally writes a simple function down on paper (i.e., f(x,y,z,t) = 5xt). I should ask one day. For my code, I try to make my object variable names longer so as to be more descriptive. There are almost certainly many places we could fix up in MOOSE and many apps though 😆